home *** CD-ROM | disk | FTP | other *** search
- Subject: Re:FW_CCommand::DoIt
- Sent: 6/2/96 12:31 PM
- Received: 6/3/96 7:58 AM
- From: Hutchings Software Development, hsd@earthlink.net
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- > Brad,
- >
- > I agree this is confusing. I'm not sure whether the answer is to have
- > execute call SaveUndoState or to remove SaveUndoState from FW_CCommand.
- > Since SaveUndoState isn't necessary for command processing, and it is
- often
- > simpler to save undo state data in a DoIt implementation, I'm leaning
- > towards removing it.
- >
- > gsf.
-
- Before removing it (and ignoring my original point momentarily :-),
- consider how easy it for developer dweebs like me to figure out how to
- implement an undoable command given the FW_CCommand class definition. The
- methods serve as a great template for developers to follow. It took me only
- a few minutes to whip up a FW_CCommand descendant, just by filling in the
- appropriately named methods with the right code.
-
- Brad
-
-
-
-
- Richard B. "Brad" Hutchings
- General Partner,
- Hutchings Software Development
-
- hsd@earthlink.net
-